-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
e2e test case: basic send *and receive* #139
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two high level requests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's hold off on deleting the bash integration tests for now. We're still deciding if there are reasonable use cases for them that the Ginkgo framework can't replicate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would agree here, lets leave the bash scripts. If we decide to remove, we can create a separate issue to remove them altogether.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
addressed in 98deca9
tests/basic_send_receive.go
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After the message is delivered from B->A, can you have the relayer redeem the reward marked in the receipt? That behavior is not currently covered by any of the existing E2E tests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just Cam's comment #139 (comment) for redeeming rewards and checking the reward amount is correct
tests/add_fee_amount.go
Outdated
// TODO: figure out why the following is reverting with message | ||
// "execution reverted: TeleporterMessenger: no reward to redeem" | ||
transaction, err := subnetATeleporterMessenger.RedeemRelayerRewards( | ||
&bind.TransactOpts{}, fundedAddress, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should use mockTokenAddress
instead of fundedAddress
. The parameter of redeemRelayerRewards
is the fee asset contract to redeem the rewards for, with the "redeemer" address being the caller of the method. So we should be sure this transaction is being sent from the account specified by the relayer as the reward redeemer, and specify the mock token as the asset being redeemed.
3034b20
to
92f938a
Compare
addresses review comment #139 (comment)
92f938a
to
e66a8d4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
addresses review comment ava-labs/icm-contracts#139 (comment)
addresses review comment ava-labs/icm-contracts#139 (comment)
No description provided.